Repository navigation
Fix ETH3D ground-truth preparation and evaluation - #51
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Preparation assigned every image the nearest available GT pose, regardless of the time difference. Images without valid GT therefore contributed incorrect reference poses to alignment and scoring. This PR excludes those unsupported frames from evaluation alignment and scoring.
Separately, GT timestamp synchronization now follows the BAD SLAM evaluator. This has a smaller effect on the scores and follows the original implementation more closely.
Changes
ETH3D-SLAM results
Pose AUC (%), before → after; higher is better.
Uncalibrated
Absolute Pose AUC (%)
Relative to the best score (%)
Before → after (change in percentage points). Each column is normalized to its best score separately before and after, using the values above.
README result update
VidMap results reported in #21 → reevaluation of the same saved trajectories with this PR (55/55 sequences):